Changes are coming to https://stigviewer.com.
Take our survey to help us understand your usage and how we can better serve you in the future.
Take Survey
The vRA PostgreSQL database must set the log_statement to all.
Overview
| Finding ID | Version | Rule ID | IA Controls | Severity |
|---|---|---|---|---|
| V-89423 | VRAU-PG-000410 | SV-100073r1_rule | Medium |
| Description |
|---|
| The removal of security objects from the database/DBMS would seriously degrade a system's information assurance posture. If such an action is attempted, it must be logged. To aid in diagnosis, it is necessary to keep track of failed attempts in addition to the successful ones. |
| STIG | Date |
|---|---|
| VMW vRealize Automation 7.x PostgreSQL Security Technical Implementation Guide | 2018-10-12 |
Details
| Check Text ( C-89115r1_chk ) |
|---|
| At the command prompt, execute the following command: # grep '^\s*log_statement\b' /storage/db/pgdata/postgresql.conf If "log_statement is not all", this is a finding. |
| Fix Text (F-96165r1_fix) |
|---|
| At the command prompt, execute the following commands: # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "ALTER SYSTEM SET log_statement TO 'all';" # /opt/vmware/vpostgres/current/bin/psql -U postgres -c "SELECT pg_reload_conf();" |